fix: migrator force modification of fields with no default value #134
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What did this pull request do?
column.DefaultValueValue.Valid = true
causes almost all fields that do not have default values when automatic migration, and this PR will repair this problem.User Case Description
go-gorm/playground#727
9 times
ALTER TABLE "users" ALTER COLUMN ...
appeared when re-migrating the model without modifications.TestReMigrate